Skip to content

Comments

Include input payload in execution events and add output schemas to reasoner examples#146

Merged
AbirAbbas merged 1 commit intomainfrom
feature/execution-event-improvements
Jan 20, 2026
Merged

Include input payload in execution events and add output schemas to reasoner examples#146
AbirAbbas merged 1 commit intomainfrom
feature/execution-event-improvements

Conversation

@AbirAbbas
Copy link
Contributor

Summary

  • Include input payload in execution status update, completion, and failure events
  • Add explicit output schemas to example reasoners for better type visibility

Changes Made

  • execute.go: Add input field to event data when publishing execution events
  • reasoners.ts: Add outputSchema configuration to analyzeSentiment and processWithNotes reasoners

Why

Event consumers can now access the original input payload alongside results, enabling better debugging and observability. The explicit output schemas in examples demonstrate best practices for typed reasoner outputs.

Test Plan

  • Run existing control-plane tests
  • Verify example reasoners work with new schema configuration

🤖 Generated with Claude Code

…easoner examples

- Include input payload in status update, completion, and failure events
- Add explicit output schemas to analyzeSentiment and processWithNotes reasoners
- Improves event data completeness for downstream consumers

Co-Authored-By: Claude <noreply@anthropic.com>
@AbirAbbas AbirAbbas merged commit aae99c2 into main Jan 20, 2026
21 checks passed
@AbirAbbas AbirAbbas deleted the feature/execution-event-improvements branch January 20, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant